Power conservation in a distributed digital video recorder/content delivery network system

ABSTRACT

A method is provided in one example embodiment and includes determining that a network storage module has resources for buffering data currently being sent to a local storage module; determining if the local storage module should enter into a power saving mode; and buffering the configurable amount of data at the network storage module while the local storage module is in the power saving mode. In more particular embodiments, the method includes communicating the configurable amount of data to the local storage module after it resumes a normal operating mode. In addition, the method may include communicating at least a portion of the configurable amount of data to the local storage module using a unicast protocol or a multicast protocol.

TECHNICAL FIELD

This disclosure relates in general to the field of energy and, more particularly, to power conservation in a distributed digital video recorder/content delivery network system.

BACKGROUND

Energy consumption has become a preeminent concern for industrialized societies. Both consumers and businesses have become aware of their energy usage. Whether motivated by altruistic reasons, or by profitability concerns, individuals have come to terms with the notion that energy is a finite commodity: a commodity having accompanying costs that should be managed. Administrators now focus on power usage and, more specifically, on how to reduce those expenditures. In recent times, device manufacturers have added instrumentation and features in the network to quell these concerns. However, as network systems have become more sophisticated and energy demands have continued to increase, a significant challenge lies in matching network capabilities with more intelligent energy consumption.

BRIEF DESCRIPTION OF THE DRAWINGS

To provide a more complete understanding of the present disclosure and features and advantages thereof, reference is made to the following description, taken in conjunction with the accompanying figures, wherein like reference numerals represent like parts, in which:

FIG. 1 is a simplified block diagram of an energy management system in accordance with one embodiment of the present disclosure;

FIG. 2A is a simplified block diagram illustrating possible example details associated with one embodiment of the present disclosure;

FIG. 2B is a simplified flow diagram illustrating potential operations associated with one embodiment of the present disclosure;

FIG. 2C is a simplified flow diagram illustrating potential operations associated with one embodiment of the present disclosure;

FIG. 2D is a simplified flow diagram illustrating potential operations associated with one embodiment of the present disclosure;

FIG. 3 is a simplified block diagram illustrating possible example details associated with one embodiment of the present disclosure; and

FIG. 4 is a simplified flow diagram illustrating potential operations associated with one embodiment of the present disclosure.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS Overview

A method is provided in one example embodiment and includes determining that a network storage module has resources for buffering data currently being sent to a local storage module. The data can be associated with video, multimedia information, audio, etc. The method also includes determining if the local storage module should enter into a power saving mode; and buffering the configurable amount of data at the network storage module while the local storage module is in the power saving mode. In more particular embodiments, the method can include communicating the configurable amount of data to the local storage module after it resumes a normal operating mode. In addition, the method may include communicating at least a portion of the configurable amount of data to the local storage module using a unicast protocol or a multicast protocol.

In specific implementations, the local storage module is provided in a digital video recorder, which resumes a normal operating mode after a predetermined time interval. Additionally, historical data of past use of the local storage module can be used to determine if the local storage module should enter into the power saving mode. A particular type of content can be evaluated as a basis for determining whether to initiate the buffering of the configurable amount of data. In certain instances, at least a portion of the configurable amount of data is cached and presented at a requested playout position, which can be identified in a request for the portion.

EXAMPLE EMBODIMENTS

FIG. 1 is a simplified block diagram of an energy management system 10 in accordance with one example implementation of the present disclosure. FIG. 1 includes a domain 14 that can include any number of devices such as wireless controllers, access points (APs), routers, switches, etc., which can be part of a network 22. Domain 14 is also coupled to a set of power management applications 12, which may include elements such as a local area network (LAN) management element. Management applications 12 can operate to intelligently control (directly or indirectly) any of a plurality of endpoints 18 being depicted in FIG. 1. A controller 20 can be provisioned in network 22 in order to execute some of the power management activities discussed herein. Controller 20 may include a network storage module 26, which can interface with a plurality of network devices 32 such as a local storage module 34. In a particular embodiment, local storage module 34 is a digital video recorder (DVD). Additionally, a gateway 28 may be provisioned in network 22 such that it can interface with a plurality of converging-IP devices 36, as is being illustrated in FIG. 1. In one particular implementation, any of the infrastructure of domain 14 can interact with a number of endpoints 18 (e.g., local storage module 34, personal computers (PCs), building controllers, wireless devices, telephones, lighting fixtures, HVAC systems, video devices (e.g., Telepresence systems), etc.).

As shown in FIG. 1, a stream source 30 may be in communication with network 22. Stream source 30 can provide a data or program stream to network 22. For ease of illustration and explanation, stream source 30 is shown in FIG. 1 as producing a single program stream. However, it should be understood that stream source 30 typically generates multiple data (or program) streams that are delivered to multiple subscribers (e.g., multiple local storage modules 34).

In accordance with the teachings of the present disclosure, energy management system 10 can be configured to command and control functions for any number of endpoints 18. Note that regardless of whether local storage module 34 is turned on or off, it typically buffers a configurable amount of data (e.g., 30 minutes of content) from a currently tuned channel such that a user can rewind and watch the buffered data (if so desired). In one embodiment, the configurable amount can be set by an administrator or an end user, where the data is a media channel. For example, the configurable amount may be set to buffer 15 minutes, 30 minutes, or 45 minutes of a current television channel being delivered to local storage module 34. Because local storage module 34 is consistently buffering the configurable amount of data, local storage module 34 is unable to go into a power saving mode; this is not energy efficient, and this shortens the life of the disk drives in local storage module 34.

In a particular embodiment of the present disclosure, network storage module 26 determines if it has enough capacity to buffer a configurable amount of data from a currently tuned channel on local storage module 34. If network storage module 26 determines that there is enough bandwidth/CPU/disk capacity to buffer the configurable amount of data, (i.e., to satisfy a potential future rewind request) network storage module 26 sends a signal to local storage module 34 to not buffer the configurable amount of data and to enter into a power saving mode (i.e., any type of energy or power reduction mode inclusive of hibernating activities, sleep modes, standby modes, etc.). The power saving mode can allow local storage module 34 to spin down disk drives and/or turn off certain other subsystems. In a particular embodiment, local conditions at local storage module 34 can be evaluated and, if local storage module 34 remains idle for an amount of time, local storage module 34 may request network storage module 26 to buffer the configurable amount of data so local storage module 34 can enter into a power savings mode.

By buffering the configurable amount of data at network storage module 26, local storage module 34 can enter into a power savings mode at off-peak times. Any rewind requests made at local storage module 34 can be fulfilled network storage module 26. When system-wide conditions merit that local storage module 34 should come back on-line (i.e., return to a normal operating mode), the configurable amount of data can be stored (or buffered) at local storage module 34 instead of at network storage module 26.

More specific to a traditional DVR set up, the DVR is unable to anticipate if a user would want to rewind a current channel at any given time. As a result, the DVR stores 30 minutes of data (buffers 30 minutes of a currently tuned channel) on the DVR's disk drive. This requires the local DVR to be systematically active: consuming energy and shortening the life of the disk drives. Energy management system 10 is configured to determine if there are sufficient network DVR resources (optionally in combination with observed local behavior) to satisfy a rewind request. If there are sufficient network resources to store or buffer the data at the network DVR, then (when appropriate) the local DVR enters into a sleep mode (or power saving mode) such that less energy is consumed. During such times, the DVR disk drives can be spun down. Hence, the DVR may be more energy efficient and the life of the disk drives in the DVR may be extended.

In operation, energy management system 10 can offer precise command and control for energy consumption associated with endpoints 18. The activities of energy management system 10 may (in certain instances) include broadcasting messages to individual endpoints 18 to shift from one power source to a different power source (e.g., during peak demand time intervals) or to enter into a power saving mode, as further discussed below. From a business perspective, the smart loading capabilities of the architecture allow for a realizable and significant cost savings. Furthermore, energy management system 10 provides a mechanism that understands the power consumption characteristics of endpoints 18 for which it has responsibility.

In operation, energy management system 10 can be configured to communicate a broadcast message that requests network devices to shift into a power saving mode. This broadcast message can be triggered in cases of excess power demand, based on specific policies, based on administrator preferences, based on cost considerations, etc. Consider an example where local storage module 34 has been turned off. Because local storage module 34 may remain active, even when turned off, network storage module 26 may be configured to determine if there are sufficient network resources (optionally in combination with observed local behavior) to put local storage module 34 into a power saving mode so less energy is consumed and the disk drives are spun down. In another example, local storage module 34 can be switched to battery power during peak usage times. Note that the term ‘resources’ is a broad term meant to encompass things such as bandwidth, CPU capacity, link availability, memory space, or any other suitable resource associated with data management.

The specific broadcast message could be formatted in any appropriate manner, provisioned as part of a standard (e.g., IETF Energy Management Standard), offered as a proprietary signaling mechanism, provisioned as part of existing signaling (e.g., discovery protocols, heartbeat messaging, keep alive messaging, type-length-value (TLV) paradigms, etc.), provisioned internally in the actual endpoints 18, which could reference a policy instructing them to switch power sources at certain times, enter into a power saving mode, etc. Any message format could be used to accommodate the energy management activities being discussed herein. This includes directing networked devices to shift energy resources in a particular fashion and/or for a particular time interval. Note that the term ‘switch’ as used herein in this Specification is broad in that it includes any type of decoupling, disconnection, interruption, withdrawal, release, suspension, detachment, or any other suitable disengagement from a first power source to a second power source or entering into a power saving mode. The individual power sources are not necessarily equivalent, but certainly could be. The particular power sources can include power bricks, batteries (external or internal), DC sources, AC sources, power outlets, generators, solar panels, or any other suitable power source, which may be based on particular needs or specific energy configurations.

In particular scenarios, the given network device (e.g., local storage module 34) can choose to ignore the broadcast message. Such conditions are dynamic and, therefore, energy management system 10 is configured to be responsive to existing environmental constraints. Additionally, it should be noted that although the examples detailed herein may involve storage devices, the broadcast messaging mechanism is valid for any networked device that is able to switch to a different power source or to enter into a power saving mode. In addition, such systems can also have different levels of power saving modes, where different components of the system are turned off or powered down to conserve power.

Logistically, a parent-child relationship can exist between the network infrastructure (e.g., a router, a switch, etc.) and its associated endpoints. Broadcast messages can be exchanged between these components at appropriate times. Any suitable management application can collect energy usage parameters (e.g., across an entire domain for which it is responsible) and, subsequently, determine the power shedding/power source switching that should occur.

Controller 20 can send out broadcast messages to endpoints 18, to selected endpoints, to selected groups of endpoints, etc. in order to instruct them that they should enter into a power saving mode (to any appropriate degree), and/or switch power sources. In one particular example, the endpoints are adapted to interpret the broadcast messages (or to interpret an internal policy) such that the endpoints can readily switch to battery usage or enter into a power saving mode (e.g., based on available bandwidth capacity at the network level, during a peak demand window, etc.). In certain implementations, the broadcast messages received by the endpoints would include an assigned time interval for the endpoints to remain on battery power or in a power saving mode.

Additional instructions can indicate particular modes for transitioning between power sources or power saving modes (e.g., transitioning to a sleep mode after disconnecting from the battery source, transitioning to a power down mode after disconnecting from the battery source, transitioning to normal operations associated with a power outlet, etc.). Note that even if the endpoints cannot necessarily accommodate a full time interval for particular mode, the endpoints can still disconnect from their current power source or enter into a power saving mode for as long as would be practical. In this sense, a broadcast message can be viewed as a suggestion in certain scenarios, and not necessarily as a strict requirement for the endpoints to follow.

The management application can alert designated endpoints to shed power or enter into a power saving mode using various communication protocols. In one example, a simple broadcast message can be used to deliver this alert over the wired network. In other instances, a wireless access point can deliver this alert wirelessly via management frames in a corresponding 802.11 message. Note that in particular use cases, the Energy Efficient Ethernet protocol (e.g., IEEE 802.3az) can be involved in such messaging. Other protocols can include proprietary mechanisms, unicasting activities, multicasting activities, simple TCP/IP communications, user datagram protocol (UDP) communications, any appropriate discovery protocol, etc.

An agent or module provisioned in endpoints 18 can interpret the broadcast message in order to switch power sources or enter into a power saving mode. In some cases, where enhanced intelligence is provided in a power source, the power source itself could actively be involved in this transitioning scenario because there can be a continued power draw (often referred to as a ‘vampire draw’) in many instances. In yet other scenarios, a personal computer could actively participate in these activities by implementing a mechanism (e.g., provisioning software, providing instructions, etc.) for the power supply, which can be configured to disconnect itself from a power source or enter into a power saving mode.

Operationally, endpoints 18 can return to a charging power outlet or to a normal operating mode based on any number of potential options. For example, one option may be associated with a timeout message provided in the broadcast message. The message would indicate, for example, to enter into a power saving mode for the next two hours. Another option would involve a second broadcast message sent to instruct the endpoint to reconnect to the grid or return to a normal operating mode. Another option would involve a timeout message based on a given power level (e.g., disconnect the endpoint until it reaches a 20% battery life). Other options can be based on the endpoint itself, where a local policy is used to instruct the endpoint when to reconnect to a power outlet or return to a normal operating mode. Still other options can involve default-timing mechanisms (specific to each endpoint 18) such that endpoints 18 would automatically shift to their normal operating mode after some predefined time interval (e.g., 20 minutes, 30 minutes, 60 minutes, etc.).

A number of advantages can be achieved by the architecture of energy management system 10. For example, the architecture is configured to intelligently control power from a network perspective. More specifically, the architecture is configured to determine when local storage module 34 does not need to buffer a configurable amount of data and subsequently put local storage module 34 into a power saving mode so less energy is consumed and the disk drives may be spun down. Additionally, there is an additional benefit to charging/discharging endpoints in the manner outlined herein, as such activities can suitably maintain a healthy device life.

In addition, the architecture of energy management system 10 allows network and network-attached equipment to take advantage of a configuration that includes no central processing and no central repository. Such a configuration also offers the advantage of having no single point of failure. The group in a cloud (i.e., the network) can be self-managed, where no central control exists. Controller 20 can be representative of a single computing device, which could be provisioned anywhere in the network, or a plurality of controllers 20 can be provisioned at strategic locations in the network, as further described below.

Further, the configuration of energy management system 10 is protocol agnostic, where virtually any communication transport can be used. The system allows cloud computing to be done to a variable number of entities (all of which may have different types of ASICS, OSs, etc.). Dynamically, endpoints 18 can join and leave the heterogeneous environment, where various types of endpoints can be readily managed by energy management system 10. As a stand-alone solution, energy management system 10 enables businesses and residences to monitor and to control the electric consumption of networking equipment. An administrator can monitor devices like switches and routers, as well as LAN switch connected Power over Ethernet (PoE) devices such as phones, access points, IP security cameras, door access equipment, etc. Energy management system 10 also has the ability to monitor and to control the energy demands of AC powered devices such as smart power distribution units, networked building systems, office equipment, etc. Energy management system 10 also includes an open interface to allow 3rd party management systems to participate in the framework.

Turning to FIG. 2A, FIG. 2A is a simplified block diagram illustrating one possible set of details associated with energy management system 10. FIG. 2A includes controller 20, network 22, network storage module 26, stream source 30, and local storage module 34. Network storage module 26 includes a network memory element 38 and a processor 40 a. Local storage module 34 includes a local memory element 42 and a processor 40 b. In a particular embodiment, local storage module 34 is a DVR. In this example, regardless of whether local storage module 34 is turned on, it stores a configurable amount of data (e.g., 30 minutes of content) from a currently tuned channel so that a user can rewind and watch the stored data if desired. This does not allow local storage module 34 to go into power saving modes, and shortens the life of the disk drives in local memory element 42.

In a particular embodiment, network storage module 26 determines if it has enough capacity to store the configurable amount of data and satisfy future rewind requests at local storage module 34. If network storage module 26 determines that there is enough spare bandwidth/CPU/disk capacity to satisfy future rewind requests, network storage module 26 sends a signal to local storage module 34 to not record the configurable amount of data, thus allowing local storage module 34 to enter into a power saving mode and possibly spin down the disk and/or turn off certain other subsystems.

By storing the configurable amount of data at network storage module 26, local memory element 42 (of local storage module 34) may be spun down at off-peak times when there is sufficient capacity to satisfy rewind requests from network storage module 26. When system-wide conditions merit that local storage module 34 returns to a normal operating mode, the configurable amount of data will be buffered in local memory element 42 instead of network storage module 26.

In a particular embodiment, local storage module 34 takes into consideration local conditions such that local storage module 34 may request network storage module 26 to buffer the configurable amount of data and local storage module 34 can enter a power savings mode. For example, local storage module 34 (or network storage module 26) may determine that local conditions indicate that local storage module 34 may be a candidate for entering a power saving mode. Two purposes of entering into the power saving mode include reducing power usage and extending the life of rotating media.

Local conditions that can indicate local storage module 34 would be a candidate for entering into a power saving mode can include no user input for a configured duration (e.g., 30 minutes, 45 minutes, 1 hour, etc.), or local storage module 34 being “turned off” (note that local memory element 42 is typically still active when local storage module 34 is “off”). Other conditions may include the use of presence systems (e.g., radio-frequency identification (RFID), cell phone usage, home automation and cloud notifications) to indicate that no users are around local storage module 34, or that the users are not home or in the same building as local storage module 34. In addition, historical data may be examined to see if a user or users have behaviors or patterns that indicate a rewind activity is likely. Certain indicators can include local storage module 34 usage at particular times of the day/week, previous activity that resulted in network storage module 26 rewind events, numerous unpredictable/unexpected rewind requests, etc. For example, a user may frequently rewind during a sporting event. Further, the availability of non-rotation storage in local storage module 34 may be evaluated: even if a lower resolution would be ultimately stored.

In an embodiment, after local storage module 34 takes into consideration local conditions, local storage module 34 may signal network storage module 26 that local storage module 34 would like to hand off the storage (i.e., perform buffering) of the configurable amount of data to network storage module 26. Network storage module 26 receives the request and analyzes current network conditions to see if capacity is available to satisfy upcoming rewind events. For example, network storage module 26 may determine if the data is already being recorded at network storage module 26 and, therefore, network storage module 26 can satisfy a request for the data (e.g., a request to rewind the channel content). If the data is not already being recorded at network storage module 26, network storage module 26 can determine if there is capacity in network memory element 38 to store (or buffer) the configurable amount of data. For example, network storage module 26 may determine if there is enough network capacity to unicast every request for data (e.g., rewind request) from local storage module 34 or if there is sufficient network resources to unicast an expected load based on the local conditions of local storage module 34. If the configurable amount of data (e.g., channel) is already being recorded and local storage module 34 requests the buffered data, the requested data may be available because network storage module 26 may be able to multicast the data to each local storage module 34 requesting the data.

For hybrid fibre-coaxial (HFC) networks, network storage module 26 may be configured to correlate the availability of quadrature amplitude modulation (QAM) channels to local storage module 34. There may be a hierarchy of QAM mapping to service groups (different local storage module 34), so knowledge of the network topology may be required. For data over cable service interface specification (DOCSIS) systems, network storage module 26 may be configured to correlate the available cable modem termination system (CMTS) bandwidth to bandwidth associated with local storage module 34. There may be a hierarchy of QAM bonding groups, so knowledge of the network topology may be involved.

In a particular embodiment, network storage module 26 and/or local storage module 34 tracks user activity over time. By tracking user activity, local storage module 34 may identify different behaviors during prime time, off-peak, and morning hours. For example, network storage module 26 and/or local storage module 34 may be configured with an adaptive scheme that learns the times at which local storage module 34 expects load. Part of this learning may include the anticipation of events with high live viewership (e.g., the National Football League (NFL) Super Bowl), or pay-per-view programs that have been purchased.

Network storage module 26 may track the likelihood that a particular local storage module 34 will trigger rewind activity from network storage module 26 by analyzing past rewind activity. In one embodiment, local storage module 34 may elect to spin down disk drives and buffer the configurable amount of data in a lower resolution format to memory/non-volatile random-access memory (NVRAM) located in local storage module 34. Local storage module 34 may also elect to enter subsystems into a power saving mode or spin down other subsystems (e.g., local transcoders or other assets). Network storage module 26 can periodically update local storage module 34 with the likelihood of being able to buffer the configurable amount of data, and local storage module 34 may periodically decide to enter resources into a power saving mode.

When a user attempts to access local storage module 34 in cases where local storage module 34 has been place in a power saving mode, the live data at a current position (the data that stream source 30 is currently communicating and local storage module 34 is currently receiving) is buffered at local memory element 42 so that the data is locally stored on local storage module 34. If the user wants to rewind and local storage module 34 does not have the user requested data locally buffered or cached, (i.e., because the data has been buffered at network storage module 26), the requested data is obtained from network storage module 26. In one embodiment, the entire buffered data is cached locally on local storage module 34 and then presented (displayed) to the user. In another embodiment, the buffered data is streamed (either unicast or multicast) to the user until local storage module 34 can present the desired playout position.

Turning to FIG. 2B, FIG. 2B is a simplified flowchart 200 illustrating example activities of local storage module 34 entering into a power saving mode. At 202, local conditions indicate that a local storage module may be a candidate for entering into a power saving mode. For example, the local conditions may be monitored by local storage module 34, network storage module 26, or both. At 204, the system can determine if a network storage module has enough resources to buffer a configurable amount of data that is being sent to the local storage module. If the network storage module does not have enough resources, then the local storage module is not shut down, as in 206.

If the network storage module does have enough resources, then the system determines if the local storage module will need to buffer or store the configurable amount of data before an event occurs, as in 208. If the local storage module will need to buffer or store the configurable amount of data before an event occurs, then the local storage module is not shut down, as in 206. If the local storage module will not need to buffer or store the configurable amount of data before an event occurs, then the local storage module enters into a power saving mode, as in 210. At 212, the configurable amount of data is buffered at the network storage module.

Turning to FIG. 2C, FIG. 2C is a simplified flowchart 201 illustrating example activities of local storage module 34 entering into a power saving mode. At 214, a given network storage module has enough resources to buffer a configurable amount of data. At 216, the system determines if local conditions indicate that a local storage module may be a candidate for entering into a power saving mode. If the local storage module is not a candidate for entering into a power saving mode, then the local storage module is not shut down, as in 218.

If the local storage module is a candidate for entering into a power saving mode, then the system determines if the local storage module will need to buffer or store the configurable amount of data before an event occurs, as in 220. If the local storage module will need to buffer or store the configurable amount of data before an event occurs, then the local storage module is not shut down, as in 218. If the local storage module will not need to buffer or store the configurable amount of data before an event occurs, then the local storage module enters into a power saving mode, as in 222. At 224, the configurable amount of data is buffered at the network storage module.

Turning to FIG. 2D, FIG. 2D is a message flow diagram of a portion of energy management system 10, showing more detail of the component interactions in the example scenario of FIG. 2A. In this particular implementation, FIG. 2D includes stream source 30, network storage module 26, and local storage module 34. As shown by an indicator 56, local storage module 34 is powered on, packets are not buffered at network storage module 26, and stream source 30 transmits packets 310-330 through network storage module 26 to local storage module 34. In this example, after packet 330 is received, local storage module 34 sends network storage module 26 a signal 58 that indicates local storage module 34 has been turned off. Network storage module 26 may interpret signal 58 that local storage module is a candidate for entering into a power saving mode, as shown by an indicator 60.

In response to signal 58, and if network storage module 26 has enough resources to buffer a configurable amount of data, network storage module 26 sends a signal 62 to local storage module 34 to enter into a power saving mode. While local storage module 34 is in a power saving mode, packets 340-360 are buffered at network storage module 26. After a period of time, local storage module 34 sends network storage module 26 a signal 66 that local storage module 34 has been turned on and is in normal operating mode, as shown by an indicator 68. Network storage module 26 sends packets 340-360 that network storage module 26 has buffered and does not buffer any more packets. In a particular embodiment, network storage module 26 only sends packets 340-360 if they are requested (i.e., a rewind request by the user). Stream source 30 transmits packet 370 and any further packets through network storage module 26 (and to local storage module 34), until local storage module 34 again enters into a power saving mode.

FIG. 3 is a simplified block diagram illustrating one embodiment of energy management system 10. FIG. 3 includes stream source 30, network 22, controllers 20 a and 20 b, network control modules 26 a and 26 b, local storage modules 34 a-d, a content delivery network 52, and an access network 54. Content delivery network 52 is a system of computers or servers containing copies of data placed at various nodes of network 22. The nodes are usually deployed in multiple locations (often over multiple backbones) and, further, can cooperate with each other to satisfy requests for content by end users (e.g., users of local storage modules 34 a-d). The number of nodes and servers making up content delivery network 52 varies depending on the architecture. Requests for content are (typically) algorithmically directed to nodes that are optimal in some way. When optimizing for performance, locations that are best for serving content to the end users may be chosen. This may be measured by choosing locations that have the fewest hops, the fewest number of network seconds away from the requesting end users, or the highest availability in terms of server performance (both current and historical), so as to optimize delivery across local networks.

Access network 54 simply refers to the series of wires, cables and equipment lying between a consumer/business termination point (the point at which a connection reaches the end users) and the local exchange. The local exchange contains banks of automated switching equipment to direct a connection to the end users. The access network may be constantly evolving, growing as new end users are connected, and as new services are offered.

When a configurable amount of data (e.g., on a channel 55) is buffered at network storage module 26 a and requested by local storage module 34 a and 34 b, network storage module 26 a (or controller 20 a) may multicast channel 56 to local storage modules 34 a and 34 b. If network storage module 26 a can multicast channel 56 to local storage modules 34 a and 34 b, then network capacity can be increased and used to buffer a different channel. In addition, network storage module 26 b may buffer a first configurable amount of data (e.g., on a channel 59) and a second configurable amount of data (e.g., on a channel 61). Network storage module 26 b (or controller 20 b) can be configured to deliver channel 59 to local storage module 34 c and channel 61 to local storage module 34 d.

Controllers 20 a and 20 b and/or network storage modules 26 a and 26 b can maintain any number of data sets (e.g., tables, lists, policies, etc.) that can be used in the management of the architecture. For example, the data can reveal a given endpoint's local storage module's 34 a-d, identification or ID, the endpoint's role, the domain of the endpoint, the importance of the endpoint, the current energy levels of the endpoints, the battery capabilities of the endpoints (e.g., their ability to shift to a battery source), the current battery levels of the endpoints (e.g., including a low battery level threshold, which can be reflective of vulnerabilities for data loss), a respective management interface for the endpoints, any respective children of the endpoints, any possible neighbors of the endpoints, the possible power saving modes of the endpoints, etc. Controllers 20 a and 20 b and/or network storage modules 26 a and 26 b can use the data sets to control multiple endpoints.

In one example implementation, each local storage module 34 a-d and/or controllers 20 a and 20 b can include software to achieve the optimal energy management operations, as outlined herein in this Specification. For example, controllers 20 a and 20 b may include software (e.g., in network storage modules 26 a and 26 b respectively), which is configured to intelligently evaluate an opportune time for sending broadcast messages to local storage modules 34 a-d (for switching between power sources or power saving modes). In example embodiments, simple network access can be leveraged to offer the capability for an end user to control energy parameters in a given domain.

Controllers 20 a and 20 b are network elements configured to interact with local storage modules 34 a-d in order to manage energy usage in energy management system 10. Note that controllers 20 a and 20 b can readily be part of a server in certain embodiments of this architecture, or provisioned in conjunction with management applications 12. As used herein in this Specification, the term ‘network element’ is meant to encompass proprietary devices, servers, network appliances, routers, switches, management appliances, gateways, bridges, loadbalancers, firewalls, processors, modules, or any other suitable device, node, proprietary component, element, or object operable to exchange information in a network environment. Moreover, the network elements may include any suitable hardware, software, components, modules, interfaces, or objects that facilitate the operations thereof. This may be inclusive of appropriate algorithms and communication protocols that allow for the effective exchange of data or information.

Software for providing intelligent energy management functionalities can be provided at various locations. In one example implementation, this software is resident in a network element (e.g., provisioned in controllers 20 a and 20 b, network storage modules 26 a and 26 b, local storage modules 34 a-d, and/or any of endpoints 18) or in another network element for which this capability is relegated. In other examples, this could involve combining domain devices, controllers 20 a and 20 b, network storage modules 26 a and 26 b, local storage modules 34 a-d, and/or other endpoints 18 with an application server, a firewall, a gateway, or some proprietary element, which could be provided in (or be proximate to) these identified network elements, or this could be provided in any other device being used in a given network. In other embodiments, each controller 20 a and 20 b, network storage module 26 a and 26 b, local storage module 34 a-d, and/or endpoint 18 may include any suitable algorithms, hardware, software, components, modules, interfaces, or objects that facilitate these energy management operations. This may be inclusive of appropriate communication protocols that allow for the effective exchange of data or information for achieving energy management in a network environment.

In still other embodiments, the energy management features may be provided externally to controllers 20 a and 20 b, network storage modules 26 a and 26 b, local storage modules 34 a-d, and/or endpoints 18, or included in some other network device, or in a computer to achieve these intended functionalities. As identified previously, a network element can include software to achieve the energy management operations, as outlined herein in this Specification. In certain example implementations, the energy management functions outlined herein may be implemented by logic encoded in one or more tangible media (e.g., embedded logic provided in an application specific integrated circuit [ASIC], digital signal processor [DSP] instructions, software [potentially inclusive of object code and source code] to be executed by a processor, or other similar machine, etc.). In some of these instances, a memory element [e.g., network memory element 38 and local memory element 42 in FIG. 2A] can store data used for the operations described herein. This includes the memory element being able to store instructions (e.g., software, logic, code, etc.) that are executed to carry out the activities described in this Specification. A processor can execute any type of instructions associated with the data to achieve the operations detailed herein in this Specification. In one example, the processor [e.g., processor 40 a and 40 b in FIG. 2A] could transform an element or an article (e.g., data) from one state or thing to another state or thing. In another example, the activities outlined herein may be implemented with fixed logic or programmable logic (e.g., software/computer instructions executed by a processor) and the elements identified herein could be some type of a programmable processor, programmable digital logic (e.g., a field programmable gate array [FPGA], an erasable programmable read only memory (EPROM), an electrically erasable programmable ROM (EEPROM)) or an ASIC that includes digital logic, software, code, electronic instructions, or any suitable combination thereof.

Any of these elements (e.g., the network elements, the endpoints, etc.) can include memory elements for storing information to be used in achieving the energy management activities as outlined herein. Additionally, each of these devices may include a processor that can execute software or an algorithm to perform the energy management activities as discussed in this Specification. These devices may further keep information in any suitable memory element [random access memory (RAM), ROM, EPROM, EEPROM, ASIC, etc.], software, hardware, or in any other suitable component, device, element, or object where appropriate and based on particular needs. Any of the memory items discussed herein should be construed as being encompassed within the broad term ‘memory element.’ Similarly, any of the potential processing elements, modules, and machines described in this Specification should be construed as being encompassed within the broad term ‘processor.’ Each of the network elements can also include suitable interfaces for receiving, transmitting, and/or otherwise communicating data or information in a network environment.

Turning to FIG. 4, FIG. 4 is a simplified flowchart 400 illustrating one potential operation associated with the present disclosure. At 402, local conditions indicate that a local storage module may be a candidate for entering into a power saving mode. The local conditions may be monitored by local storage module 34, network storage module 26, or both. At 404, the system determines if a network storage module has enough resources to buffer a configurable amount of data that is currently being sent to the local storage module. If the network storage module does not have enough resources, then the local storage module is not shut down, as in 406.

If the network storage module does have enough resources, then the system determines if the local storage module will need to buffer or store the configurable amount of data before an event occurs, as is illustrated in 408. If the local storage module will need to buffer or store the configurable amount of data before an event occurs, then the local storage module is not shut down, as in 406. If the local storage module will not need to buffer or store the configurable amount of data before an event occurs, then the local storage module's memory is shut down and the local storage module is powered off, as in 410. At 412, the configurable amount of data is buffered at the network storage module.

At 414, the system determines if the local storage module has returned to a normal operating mode. If the local storage module has not returned to a normal operating mode, then the configurable amount of data continues to be buffered at the network storage module, as in 412. If the local storage module has returned to a normal operating mode, then the buffered data is sent to the local storage module, as illustrated in 416. In a particular embodiment, the buffered data is only sent to the local storage module if a request is received for the buffered or stored data. At 418, the configurable amount of data is not buffered at the network storage module.

Logistically, certain items or elements can be provisioned for the intelligent energy management system to function. For example, the enabled endpoints of FIG. 1 can include an agent (for example, in software) that allows these endpoints to respond to messages from the network. Note that the term ‘message’ as used herein in this Specification is meant to encompass any type of signaling, packet information, broadcasting, short message service (SMS) communications, instant messaging (IM), e-mail protocols, or any other message type that can be delivered to an endpoint such that it understands to switch between available power sources.

Note that with the examples provided above, interaction may be described in terms of two, three, or four network elements. However, this has been done for purposes of clarity and example only. In certain cases, it may be easier to describe one or more of the functionalities of a given set of flows by only referencing a limited number of network elements. It should be appreciated that energy management system 10 (and its teachings) are readily scalable and, further, can accommodate a large number of components, as well as more complicated/sophisticated arrangements and configurations. Accordingly, the examples provided should not limit the scope or inhibit the broad teachings of energy management system 10, as potentially applied to a myriad of other architectures.

It is also important to note that the steps in the preceding FIGURES illustrate only some of the possible scenarios that may be executed by, or within, energy management system 10. Some of these steps may be deleted or removed where appropriate, or these steps may be modified or changed considerably without departing from the scope of the present disclosure. In addition, a number of these operations have been described as being executed concurrently with, or in parallel to, one or more additional operations. However, the timing of these operations may be altered considerably. The preceding operational flows have been offered for purposes of example and discussion. Substantial flexibility is provided by energy management system 10 in that any suitable arrangements, chronologies, configurations, and timing mechanisms may be provided without departing from the teachings of the present disclosure.

Although the present disclosure has been described in detail with reference to particular arrangements and configurations, these example configurations and arrangements may be changed significantly without departing from the scope of the present disclosure. For example, although the present disclosure has been described with reference to particular communication exchanges involving certain protocols (e.g., UDP, SSL, SNMP, etc.), energy management system 10 may be applicable to other exchanges and protocols in which data are exchanged in order to provide energy management operations. In addition, although energy management system 10 has been illustrated with reference to particular elements and operations that facilitate the communication process, these elements and operations may be replaced by any suitable architecture or process that achieves the intended functionality of energy management system 10.

Numerous other changes, substitutions, variations, alterations, and modifications may be ascertained to one skilled in the art and it is intended that the present disclosure encompass all such changes, substitutions, variations, alterations, and modifications as falling within the scope of the appended claims. In order to assist the United States Patent and Trademark Office (USPTO) and, additionally, any readers of any patent issued on this application in interpreting the claims appended hereto, Applicant wishes to note that the Applicant: (a) does not intend any of the appended claims to invoke paragraph six (6) of 35 U.S.C. section 112 as it exists on the date of the filing hereof unless the words “means for” or “step for” are specifically used in the particular claims; and (b) does not intend, by any statement in the specification, to limit this disclosure in any way that is not otherwise reflected in the appended claims. 

1. A method, comprising: determining that a network storage module has resources for buffering data currently being sent to a local storage module; determining if the local storage module should enter into a power saving mode; and buffering the configurable amount of data at the network storage module while the local storage module is in the power saving mode.
 2. The method of claim 1, further comprising: communicating the configurable amount of data to the local storage module after it resumes a normal operating mode.
 3. The method of claim 1, further comprising: communicating at least a portion of the configurable amount of data to the local storage module using a unicast protocol or a multicast protocol.
 4. The method of claim 1, wherein the local storage module is provided in a digital video recorder, which resumes a normal operating mode after a predetermined time interval.
 5. The method of claim 1, wherein historical data of past use of the local storage module is used to determine if the local storage module should enter into the power saving mode.
 6. The method of claim 1, wherein a particular type of content is evaluated as a basis for determining whether to initiate the buffering of the configurable amount of data.
 7. The method of claim 1, wherein at least a portion of the configurable amount of data is cached and presented at a requested playout position identified in a request for the portion.
 8. Logic encoded in one or more non-transitory media that includes code for execution and when executed by a processor is operable to perform operations, comprising: determining that a network storage module has resources for buffering data currently being sent to a local storage module; determining if the local storage module should enter into a power saving mode; and buffering the configurable amount of data at the network storage module while the local storage module is in the power saving mode.
 9. The logic of claim 8, the operations further comprising: communicating the configurable amount of data to the local storage module after it resumes a normal operating mode.
 10. The logic of claim 8, the operations further comprising: communicating at least a portion of the configurable amount of data to the local storage module using a unicast protocol or a multicast protocol.
 11. The logic of claim 8, wherein the local storage module is provided in a digital video recorder, which resumes a normal operating mode after a predetermined time interval.
 12. The logic of claim 8, wherein historical data of past use of the local storage module is used to determine if the local storage module should enter into the power saving mode.
 13. The logic of claim 8, wherein a particular type of content is evaluated as a basis for determining whether to initiate the buffering of the configurable amount of data.
 14. The logic of claim 8, wherein at least a portion of the configurable amount of data is cached and presented at a requested playout position identified in a request for the portion.
 15. An apparatus, comprising: a memory element configured to store data; a processor operable to execute instructions associated with the data; a network storage module configured to interface with the memory element and the processor such that the apparatus is configured for: determining that the network storage module has resources for buffering data currently being sent to a local storage module; determining if the local storage module should enter into a power saving mode; and buffering the configurable amount of data at the network storage module while the local storage module is in the power saving mode.
 16. The apparatus of claim 15, the apparatus further configured for: communicating the configurable amount of data to the local storage module after it resumes a normal operating mode.
 17. The apparatus of claim 15, the apparatus being further configured for: communicating at least a portion of the configurable amount of data to the local storage module using a unicast protocol or a multicast protocol.
 18. The apparatus of claim 15, wherein historical data of past use of the local storage module is used to determine if the local storage module should enter into the power saving mode.
 19. The apparatus of claim 15, wherein a particular type of content is evaluated as a basis for determining whether to initiate the buffering of the configurable amount of data.
 20. The apparatus of claim 15, wherein at least a portion of the configurable amount of data is cached and presented at a requested playout position identified in a request for the portion. 